Perforce QAC Eclipse Known Issues
The following list summarizes extant issues within Perforce QAC Eclipse.
- After upgrading Perforce QAC Eclipse, when trying to use a pre-existing workspace, the Perforce perspective and/or views might not be available (their content will be marked with error). Since this issue is related to deprecated preferences in the existing workspace, consider setting up a new workspace. In case you want to continue using the existing work space, close all old perspectives/views manually, and reopen them from the Windows -> Open Perspective -> Other... for the perspective and/or Windows -> Show View -> Other... for the views.
- From Eclipse Neon upwards, a option has been added labeled Expand vertical ruler icons upon hovering. This option must be enabled to allow diagnostic icons to expand and show tool tips when hovering over diagnostic icons within the annotated source. To find this option proceed to Window -> Preferences -> C/C++ -> Editor -> Hovers within eclipse.
- Help sub-menu items are disabled in Eclipse Juno.
- When the capitalization of a file name is changed on a case-insensitive file system, the results and the project will be invalid. To fix, it is required to recreate or resync the project and perform analysis again.
- If the location of an Eclipse project contains spaces in the path, during the conversion to Perforce project the conversion wizard incorrectly suggests a truncated path as location for Perforce folder location. Correct the path by editing it directly in the text box.
- Eclipse may hang when you go to close it under certain circumstances (ticket 35083). To prevent this do not disable the "Are you sure" prompt when exiting Eclipse. If you have already disabled the prompt, then you can reset the option in Eclipse: select Window > Preferences from the main Workbench menu bar, in the Preferences Dialog select General > Startup and Shutdown and select “Confirm exit when closing last window”.
- When using older versions of Eclipse, setting the Diagnostics Per Page to the maximum value (100000) can cause the plugin to hang. A maximum value of 10000 is recommended. This is being tracked under QCT-60886 and will be resolved in a future release.